What is broccoli-caching-writer?
The broccoli-caching-writer package is a Broccoli plugin that provides a base class for Broccoli plugins that need to cache their output. It helps in optimizing build times by caching the results of expensive operations and reusing them when the input hasn't changed.
What are broccoli-caching-writer's main functionalities?
Caching Output
This feature allows you to create a custom Broccoli plugin that caches its output. The `updateCache` method is where you perform your expensive operations, and the results are cached for future builds.
const CachingWriter = require('broccoli-caching-writer');
const fs = require('fs');
class MyCachingWriter extends CachingWriter {
updateCache(srcDir, destDir) {
// Perform expensive operations here
fs.writeFileSync(`${destDir}/output.txt`, 'Cached content');
}
}
module.exports = MyCachingWriter;
Handling Multiple Input Nodes
This feature allows you to handle multiple input nodes. The `updateCache` method receives an array of source directories, enabling you to process multiple inputs and cache their results.
const CachingWriter = require('broccoli-caching-writer');
const fs = require('fs');
class MultiInputCachingWriter extends CachingWriter {
constructor(inputNodes, options) {
super(inputNodes, options);
}
updateCache(srcDirs, destDir) {
// srcDirs is an array of input directories
srcDirs.forEach((srcDir, index) => {
fs.writeFileSync(`${destDir}/output${index}.txt`, `Cached content from ${srcDir}`);
});
}
}
module.exports = MultiInputCachingWriter;
Custom Cache Key
This feature allows you to define a custom cache key for your plugin. The `cacheKey` method generates a unique key that can be used to determine if the cache should be invalidated.
const CachingWriter = require('broccoli-caching-writer');
const fs = require('fs');
const crypto = require('crypto');
class CustomCacheKeyWriter extends CachingWriter {
constructor(inputNodes, options) {
super(inputNodes, options);
}
cacheKey() {
// Generate a custom cache key
return crypto.createHash('md5').update('custom-key').digest('hex');
}
updateCache(srcDir, destDir) {
fs.writeFileSync(`${destDir}/output.txt`, 'Cached content with custom key');
}
}
module.exports = CustomCacheKeyWriter;
Other packages similar to broccoli-caching-writer
broccoli-plugin
The broccoli-plugin package provides a base class for Broccoli plugins, similar to broccoli-caching-writer but without built-in caching functionality. It is more general-purpose and can be extended to create various types of Broccoli plugins.
broccoli-persistent-filter
The broccoli-persistent-filter package is another Broccoli plugin base class that provides persistent caching. It is designed for plugins that need to filter files and cache the results, similar to broccoli-caching-writer but with a focus on filtering operations.
broccoli-funnel
The broccoli-funnel package is used to funnel files from one Broccoli tree to another. While it doesn't provide caching, it is often used in conjunction with caching plugins to optimize build processes by selecting specific files or directories.
Broccoli Caching Writer
Drop-in-replacement for
broccoli-writer adding a thin
caching layer based on the computed hash of the input directory trees. If any
file in an input node has changed, the build
method will be called,
otherwise (if input is the same) the results of the last build
call will be
used instead.
Example
var Plugin = require('broccoli-caching-writer');
MyPlugin.prototype = Object.create(Plugin.prototype);
MyPlugin.prototype.constructor = MyPlugin;
function MyPlugin(inputNodes, options) {
options = options || {};
Plugin.call(this, inputNodes, {
annotation: options.annotation
});
}
MyPlugin.prototype.build = function() {
};
Documentation
new CachingWriter(inputNodes, options)
Call this base class constructor from your subclass constructor.
plugin.listFiles
list files matched, helpful as it allows us avoid a second glob
plugin.listEntries
list entries (stat objects) of files matched, helpful when further FS information is required on rebuild.
ZOMG!!! TESTS?!?!!?
I know, right?
Running the tests:
npm install
npm test
License
This project is distributed under the MIT license.